Skip to content

fix(project): avoid password file reads in dry-run update#54

Open
JerryNee wants to merge 1 commit into
TestSprite:mainfrom
JerryNee:fix/project-update-dry-run-password-file
Open

fix(project): avoid password file reads in dry-run update#54
JerryNee wants to merge 1 commit into
TestSprite:mainfrom
JerryNee:fix/project-update-dry-run-password-file

Conversation

@JerryNee

Copy link
Copy Markdown

Summary

  • keep project update --dry-run from reading --password-file before the dry-run preview
  • compute updatedFields from supplied flags, then resolve password file contents only on the real PATCH path
  • add unit and subprocess regression coverage for a missing password file under dry-run

Repro

Before this change, testsprite project update proj_anything --password-file /tmp/missing --dry-run --output json exited 1 with a raw ENOENT, even though dry-run is documented to skip filesystem writes/reads. After this change it exits 0 and previews updatedFields: ["password"].

Verification

  • npm test -- src/commands/project.test.ts
  • npm test -- test/cli.subprocess.test.ts
  • npm run typecheck
  • npm run lint
  • npm test
  • npm run build
  • node dist/index.js project update proj_anything --password-file /tmp/definitely-not-here-testsprite --dry-run --output json

@zeshi-du

Copy link
Copy Markdown
Contributor

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@zeshi-du, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 11add268-7822-43b3-9b81-49f08e4568c4

📥 Commits

Reviewing files that changed from the base of the PR and between 15e95de and fd4cfb3.

📒 Files selected for processing (3)
  • src/commands/project.test.ts
  • src/commands/project.ts
  • test/cli.subprocess.test.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants